Log event management mechanism

ABSTRACT

Techniques and structures to facilitate management of log event messages, including transmitting one or more messages, each having a unique identifier (ID), to a computing device, generating a comparison checksum for each of the one or more messages, wherein each comparison checksum is associated with a unique ID corresponding to a message from which the comparison checksum was generated, performing an encryption on each comparison checksum and associated unique ID to generate encryption data and transmitting the encryption data to the computing device.

TECHNICAL FIELD

One or more implementations relate generally to network security and,more specifically, to managing the content of event messages.

BACKGROUND

An event log is a basic resource that helps provide information aboutnetwork traffic, usage and other conditions, which stores data forretrieval by security professionals or automated security systems toassist network administrators manage various aspects, such as security,performance and transparency. Accordingly, an event log is a “log book”that can capture many different types of information (e.g., logonsessions to a network, account lockouts, failed passwords, etc.), aswell as record application events (e.g., application errors, closures,etc.). However, messages in an event log may be manipulated (eitheraccidentally or manually) by unauthorized users and/or malware.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following drawings like reference numbers are used to refer tolike elements. Although the following figures depict various examples,one or more implementations are not limited to the examples depicted inthe figures.

FIG. 1 illustrates one embodiment of a system;

FIGS. 2A & 2B illustrate embodiments of a log event management mechanismimplemented in computing devices;

FIG. 3 illustrates one embodiment of log emitter;

FIG. 4 is a flow diagram illustrating one embodiment of a processperformed by a log emitter;

FIG. 5 illustrates one embodiment of a flow between a log emitter and alog collector;

FIG. 6 illustrates one embodiment of log collector;

FIG. 7 is a flow diagram illustrating one embodiment of a processperformed by a log collector;

FIG. 8 illustrates a computer system according to one embodiment;

FIG. 9 illustrates an environment wherein an on-demand database servicemight be used according to one embodiment; and

FIG. 10 illustrates elements of environment of FIG. 9 and variouspossible interconnections between these elements according to oneembodiment.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth.However, embodiments of the invention may be practiced without thesespecific details. In other instances, well-known structures andtechniques have not been shown in detail in order not to obscure theunderstanding of this description.

Methods and systems are provided to facilitate management of log eventmessages. In embodiments, a log event message is assigned uniqueidentifier (ID) prior to transmission to a computing device. In furtherembodiments a comparison checksum is generated for the log eventmessage, and is associated with a unique ID corresponding to the logevent message from. In yet further embodiments, an encryption on eachcomparison checksum and associated unique ID is performed to generateencryption data prior to transmitting the encryption data to thecomputing device.

In other embodiments, the log event message is received at the computingdevice where a message checksum is generated and associated with theassociated unique ID. Subsequently, the encryption data is received fromthe computing device and is decrypted to extract one or more comparisonchecksums. A comparison checksum is then compared to the messagechecksum based on the Unique ID to detect whether the log event messagehas been modified.

It is contemplated that embodiments and their implementations are notmerely limited to multi-tenant database system (“MTDBS”) and can be usedin other environments, such as a client-server system, a mobile device,a personal computer (“PC”), a web services environment, etc. However,for the sake of brevity and clarity, throughout this document,embodiments are described with respect to a multi-tenant databasesystem, such as Salesforce.com®, which is to be regarded as an exampleof an on-demand services environment. Other on-demand servicesenvironments include Salesforce® Exact Target Marketing Cloud™.

As used herein, a term multi-tenant database system refers to thosesystems in which various elements of hardware and software of thedatabase system may be shared by one or more customers. For example, agiven application server may simultaneously process requests for a greatnumber of customers, and a given database table may store rows for apotentially much greater number of customers. As used herein, the termquery plan refers to a set of steps used to access information in adatabase system.

Embodiments are described with reference to an embodiment in whichtechniques for facilitating management of data in an on-demand servicesenvironment are implemented in a system having an application serverproviding a front end for an on-demand database service capable ofsupporting multiple tenants, embodiments are not limited to multi-tenantdatabases nor deployment on application servers. Embodiments may bepracticed using other database architectures, i.e., ORACLE®, DB2® by IBMand the like without departing from the scope of the embodimentsclaimed.

FIG. 1 illustrates one embodiment of a system 100 having a computingdevice employing a log event management mechanism 110. In oneembodiment, computing device 120 includes a host server computer servinga host machine. The term “user” may refer to a system user, such as(without limitation) a software/application developer, a systemadministrator, a database administrator, an information technologyprofessional, a program manager, product manager, etc. The term “user”may further refer to an end-user, such as (without limitation) one ormore of customer organizations 121A-N and/or their representatives(e.g., individuals or groups working on behalf of one or more ofcustomer organizations 121A-N), such as a salesperson, a sales manager,a product manager, an accountant, a director, an owner, a president, asystem administrator, a computer programmer, an information technology(“IT”) representative, etc.

In one embodiment, computing device 120 may serve as a service providercore (e.g., Salesforce.com® core) in communication with one or moredatabase(s) 140, one or more client computers 130A-N, over one or morenetwork(s) 135, and any number and type of dedicated nodes. Computingdevice 120 may include (without limitation) server computers (e.g.,cloud server computers, etc.), desktop computers, cluster-basedcomputers, set-top boxes (e.g., Internet-based cable television set-topboxes, etc.), etc. Computing device 120 includes an operating system(“OS”) 106 serving as an interface between one or more hardware/physicalresources of computing device 120 and one or more client devices130A-130N, etc. Computing device 120 further includes processor(s) 102,memory 104, input/output (“I/O”) sources 108, such as touchscreens,touch panels, touch pads, virtual or regular keyboards, virtual orregular mice, etc.

In one embodiment, host organization 101 may further employ a productionenvironment that is communicably interfaced with client devices 130A-Nthrough host organization 101. Client devices 130A-N may include(without limitation) customer organization-based server computers,desktop computers, laptop computers, mobile computing devices, such assmartphones, tablet computers, personal digital assistants, e-readers,media Internet devices, smart televisions, television platforms,wearable devices (e.g., glasses, watches, bracelets, smartcards,jewelry, clothing items, etc.), media players, global positioningsystem-based navigation systems, cable setup boxes, etc.

In one embodiment, the illustrated multi-tenant database system 150includes database(s) 140 to store (without limitation) information,relational tables, datasets, and underlying database records havingtenant and user data therein on behalf of customer organizations 121A-N(e.g., tenants of multi-tenant database system 150 or their affiliatedusers). In alternative embodiments, a client-server computingarchitecture may be utilized in place of multi-tenant database system150, or alternatively, a computing grid, or a pool of work servers, orsome combination of hosted computing architectures may be utilized tocarry out the computational workload and processing that is expected ofhost organization 101.

The illustrated multi-tenant database system 150 is shown to include oneor more of underlying hardware, software, and logic elements 145 thatimplement, for example, database functionality and a code executionenvironment within host organization 101. In accordance with oneembodiment, multi-tenant database system 150 further implementsdatabases 140 to service database queries and other data interactionswith the databases 140. In one embodiment, hardware, software, and logicelements 145 of multi-tenant database system 150 and its other elements,such as a distributed file store, a query interface, etc., may beseparate and distinct from customer organizations (121A-121N) whichutilize the services provided by host organization 101 by communicablyinterfacing with host organization 101 via network(s) 135 (e.g., cloudnetwork, the Internet, etc.). In such a way, host organization 101 mayimplement on-demand services, on-demand database services, cloudcomputing services, etc., to subscribing customer organizations121A-121N.

In some embodiments, host organization 101 receives input and otherrequests from a plurality of customer organizations 121A-N over one ormore networks 135; for example, incoming search queries, databasequeries, application programming interface (“API”) requests,interactions with displayed graphical user interfaces and displays atclient devices 130A-N, or other inputs may be received from customerorganizations 121A-N to be processed against multi-tenant databasesystem 150 as queries via a query interface and stored at a distributedfile store, pursuant to which results are then returned to an originatoror requestor, such as a user of client devices 130A-N at any of customerorganizations 121A-N.

As aforementioned, in one embodiment, each customer organization 121A-Nis an entity selected from a group consisting of a separate and distinctremote organization, an organizational group within host organization101, a business partner of host organization 101, a customerorganization 121A-N that subscribes to cloud computing services providedby host organization 101, etc.

In one embodiment, requests are received at, or submitted to, a webserver within host organization 101. Host organization 101 may receive avariety of requests for processing by host organization 101 and itsmulti-tenant database system 150. For example, incoming requestsreceived at the web server may specify which services from hostorganization 101 are to be provided, such as query requests, searchrequest, status requests, database transactions, graphical userinterface requests and interactions, processing requests to retrieve,update, or store data on behalf of one of customer organizations 121A-N,code execution requests, and so forth. Further, the web-server at hostorganization 101 may be responsible for receiving requests from variouscustomer organizations 121A-N via network(s) 135 on behalf of the queryinterface and for providing a web-based interface or other graphicaldisplays to one or more end-user client devices 130A-N or machinesoriginating such data requests.

Further, host organization 101 may implement a request interface via theweb server or as a stand-alone interface to receive requests packets orother requests from the client devices 130A-N. The request interface mayfurther support the return of response packets or other replies andresponses in an outgoing direction from host organization 101 to one ormore client devices 130A-N.

It is to be noted that any references to software codes, data and/ormetadata (e.g., Customer Relationship Model (“CRM”) data and/ormetadata, etc.), tables (e.g., custom object table, unified indextables, description tables, etc.), computing devices (e.g., servercomputers, desktop computers, mobile computers, such as tabletcomputers, smartphones, etc.), software development languages,applications, and/or development tools or kits (e.g., Force.com®,Force.com Apex™ code, JavaScript™, jQuery™, Developerforce™,Visualforce™, Service Cloud Console Integration Toolkit (“IntegrationToolkit” or “Toolkit”), Platform on a Service™ (“PaaS”), Chatter®Groups, Sprint Planner®, MS Project®, etc.), domains (e.g., Google®,Facebook®, LinkedIn®, Skype®, etc.), etc., discussed in this documentare merely used as examples for brevity, clarity, and ease ofunderstanding and that embodiments are not limited to any particularnumber or type of data, metadata, tables, computing devices, techniques,programming languages, software applications, software developmenttools/kits, etc.

It is to be noted that terms like “node”, “computing node”, “server”,“server device”, “cloud computer”, “cloud server”, “cloud servercomputer”, “machine”, “host machine”, “device”, “computing device”,“computer”, “computing system”, “multi-tenant on-demand data system”,“multi-tenant database system” and the like, may be used interchangeablythroughout this document. It is to be further noted that terms like“code”, “software code”, “application”, “software application”,“program”, “software program”, “package”, “software code”, “code”, and“software package” may be used interchangeably throughout this document.Moreover, terms like “job”, “input”, “request”, and “message” may beused interchangeably throughout this document.

FIGS. 2A & 2B illustrate embodiments of a log event management mechanism110 hosted by server 120 (e.g., 110(A)) and client 130 (e.g., 110(B))computing devices, respectively. According to embodiments shown in bothFIGS. 2A & 2B, management mechanism 110 includes a log emitter 212 and alog collector 215. In such embodiments, log emitter 212 transmits logevent messages to another computing device via a network (e.g., network135), which are received at a log collector 215 for processing at thecomputing device. For instance, log collector 215(A) at server computer120 may receive log event messages from log emitter 212(B) at clientcomputer 130. In other embodiments, server 120 may implement log emitter212(A) to transmit log event messages to other computing systems, whileclient 130 may receive log event messages via log collector 215(B).

FIG. 3 illustrates one embodiment of a log emitter 212. As shown in FIG.3, log emitter 212 includes identifier (ID) generation logic 310,checksum generator 320 and encryption logic 330. According to oneembodiment, ID generation logic 310 generates and assigns a unique ID(or UUID) to each log event message at log emitter 212. In oneembodiment, ID generation logic 310 may include the UUIDs within the logevent messages. Checksum generator 320 performs a checksum algorithm tocalculate a checksum derived from each log event message, resulting in acomparison checksum. In one embodiment, each comparison checksum islinked with the UUID corresponding to the log event message from whichthe checksum was generated. The resulting comparison checksum and UUIDpairs are stored as a batch.

Encryption module 330 encrypts each comparison checksum and UUID pair inthe batch to generate encrypted data for transmission to a log collector215 at another computing device. In one embodiment, encryption module330 applies a Salt algorithm to the batch of checksum and UUID pairs. Ina further embodiment, encryption module 330 may also perform symmetrickey encryption on the batch in which the symmetric key and Salt areencrypted with a public key associated with the log collector 215 towhich the encrypted message data is to be transmitted. However otherembodiments may feature an implementation of different cryptographicalgorithms by encryption module 330.

FIG. 4 is a flow diagram of a method 400 illustrating one embodiment ofa process performed by a log emitter 212. Method 400 may be performed byprocessing logic that may comprise hardware (e.g., circuitry, dedicatedlogic, programmable logic, etc.), software (such as instructions run ona processing device), or a combination thereof. The processes of method400 are illustrated in linear sequences for brevity and clarity inpresentation; however, it is contemplated that any number of them can beperformed in parallel, asynchronously, or in different orders. Further,for brevity, clarity, and ease of understanding, many of the componentsand processes described with respect to FIGS. 1-3 may not be repeated ordiscussed hereafter.

Method 400 begins at processing block 410, where a UUID is assigned toeach of one or more log event messages deposited at log emitter 212. Asshown in FIG. 5, UUID1-UUID3 are associated with Message1-Message3,respectively. At processing block 420, the log event messages aretransmitted to a log collector 215 (e.g., individually or as a batch).At processing block 430, a comparison checksum is generated for each ofthe log event messages. At processing block 440, the comparisonchecksums and associated UUIDs (or checksum UUID pairs) are stored as abatch. At processing block 450, the batch of comparison checksum UUIDpairs are encrypted to generate encrypted data. At processing block 460,the encrypted data is transmitted to a log collector 215. FIG. 5 showsthe encryption and transmission to log emitter 212. As shown in FIG. 5,the encrypted data is transmitted from log emitter 212 as a separatebatch processing workflow via a separate (or side) channel from thetransmitted log event messages.

FIG. 6 illustrates one embodiment of log collector 215, which includeschecksum generator 620, decryption logic 630, compare logic 640 andreport module 650. According to one embodiment, log collector 215 storeseach log event message received from log emitter 212 along with theassociated UUID. In embodiments in which the UUID is included within thelog event message, log collector 215 extracts the UUID. In still otherembodiments, UUIDs may not be implemented. As a result, only log eventmessages are received at log collector 215.

Checksum generator 620 performs the checksum algorithm to calculatechecksums to generate a message checksum corresponding to each log eventmessage, which is stored with the log event message and associated UUID(e.g., in embodiments in which UUIDs are implemented). At some timelater log collector 215 receives the encrypted data from log emitter212. As discussed above, the encrypted data is received from log emitter212 via a separate channel from the received log event messages.Decryption logic 630 decrypts the encrypted batch of data to extract thecomparison checksum and UUID pairs.

Compare logic 640 compares the comparison checksums with the storedmessage checksums. In one embodiment, compare logic 640 receives anextracted comparison checksum and uses the associated UUID to retrievethe message checksum having the same UUID. Subsequently, compare logic640 performs the comparison between the message checksum and thecomparison checksum to determine whether there is a match. Report module650 tracks and generates a report of the result of each performedchecksum comparison. As a result, a user may determine whether one ormore log event message have been modified sometime after transmissionfrom log emitter 212.

FIG. 7 is a flow diagram of a method 700 illustrating one embodiment ofa process performed by a log collector 215. Method 700 may be performedby processing logic that may comprise hardware (e.g., circuitry,dedicated logic, programmable logic, etc.), software (such asinstructions run on a processing device), or a combination thereof. Theprocesses of method 700 are illustrated in linear sequences for brevityand clarity in presentation; however, it is contemplated that any numberof them can be performed in parallel, asynchronously, or in differentorders. Further, for brevity, clarity, and ease of understanding, manyof the components and processes described with respect to FIGS. 1-6 maynot be repeated or discussed hereafter.

Method 700 begins at processing block 710, where a log event message isreceived and stored with the associated UUID at log collector 215. Atprocessing block 720, a message checksum is calculated and stored withthe associated UUID. FIG. 5 shows Message1 with associated UUID1 beingreceived at log collector 215, and a checksum being calculated. The sameprocess is repeated as Message2 and Message3 are received. At processingblock 730, the encrypted message data is received. At processing block740, the encrypted batch of data is decrypted to extract the comparisonchecksums. At processing block 750, each checksum message is compared toa corresponding comparison checksum to determine whether a modificationhas been detected. At processing block 760, the comparison results arereported.

FIG. 8 illustrates a diagrammatic representation of a machine 900 in theexemplary form of a computer system, in accordance with one embodiment,within which a set of instructions, for causing the machine 900 toperform any one or more of the methodologies discussed herein, may beexecuted. Machine 900 is the same as or similar to computing devices120, 130A-N of FIG. 1. In alternative embodiments, the machine may beconnected (e.g., networked) to other machines in a network (such as hostmachine 120 connected with client machines 130A-N over network(s) 135 ofFIG. 1), such as a cloud-based network, Internet of Things (IoT) orCloud of Things (CoT), a Local Area Network (LAN), a Wide Area Network(WAN), a Metropolitan Area Network (MAN), a Personal Area Network (PAN),an intranet, an extranet, or the Internet. The machine may operate inthe capacity of a server or a client machine in a client-server networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment or as a server or series of servers within anon-demand service environment, including an on-demand environmentproviding multi-tenant database storage services. Certain embodiments ofthe machine may be in the form of a personal computer (PC), a tablet PC,a set-top box (STB), a Personal Digital Assistant (PDA), a cellulartelephone, a web appliance, a server, a network router, switch orbridge, computing system, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine. Further, while only a single machine is illustrated,the term “machine” shall also be taken to include any collection ofmachines (e.g., computers) that individually or jointly execute a set(or multiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The exemplary computer system 900 includes a processor 902, a mainmemory 504 (e.g., read-only memory (ROM), flash memory, dynamic randomaccess memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM(RDRAM), etc., static memory such as flash memory, static random accessmemory (SRAM), volatile but high-data rate RAM, etc.), and a secondarymemory 918 (e.g., a persistent storage device including hard disk drivesand persistent multi-tenant data base implementations), whichcommunicate with each other via a bus 930. Main memory 904 includesemitted execution data 924 (e.g., data emitted by a logging framework)and one or more trace preferences 923 which operate in conjunction withprocessing logic 926 and processor 902 to perform the methodologiesdiscussed herein.

Processor 902 represents one or more general-purpose processing devicessuch as a microprocessor, central processing unit, or the like. Moreparticularly, the processor 902 may be a complex instruction setcomputing (CISC) microprocessor, reduced instruction set computing(RISC) microprocessor, very long instruction word (VLIW) microprocessor,processor implementing other instruction sets, or processorsimplementing a combination of instruction sets. Processor 902 may alsobe one or more special-purpose processing devices such as an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA), a digital signal processor (DSP), network processor, or thelike. Processor 902 is configured to execute the processing logic 926for performing the operations as described with reference to FIG. 1 andother Figures discussed herein.

The computer system 900 may further include a network interface card908. The computer system 900 also may include a user interface 910 (suchas a video display unit, a liquid crystal display (LCD), or a cathoderay tube (CRT)), an alphanumeric input device 912 (e.g., a keyboard), acursor control device 914 (e.g., a mouse), and a signal generationdevice 916 (e.g., an integrated speaker). The computer system 900 mayfurther include peripheral device 936 (e.g., wireless or wiredcommunication devices, memory devices, storage devices, audio processingdevices, video processing devices, etc. The computer system 900 mayfurther include a Hardware based API logging framework 934 capable ofexecuting incoming requests for services and emitting execution dataresponsive to the fulfillment of such incoming requests.

The secondary memory 918 may include a machine-readable storage medium(or more specifically a machine-accessible storage medium) 931 on whichis stored one or more sets of instructions (e.g., software 922)embodying any one or more of the methodologies as described withreference to FIG. 1, respectively, and other figures discussed herein.The software 522 may also reside, completely or at least partially,within the main memory 904 and/or within the processor 902 duringexecution thereof by the computer system 900, the main memory 904 andthe processor 902 also constituting machine-readable storage media. Thesoftware 922 may further be transmitted or received over a network 920via the network interface card 908. The machine-readable storage medium931 may include transitory or non-transitory machine-readable storagemedia.

Portions of various embodiments may be provided as a computer programproduct, which may include a computer-readable medium having storedthereon computer program instructions, which may be used to program acomputer (or other electronic devices) to perform a process according tothe embodiments. The machine-readable medium may include, but is notlimited to, floppy diskettes, optical disks, compact disk read-onlymemory (CD-ROM), and magneto-optical disks, ROM, RAM, erasableprogrammable read-only memory (EPROM), electrically EPROM (EEPROM),magnet or optical cards, flash memory, or other type ofmedia/machine-readable medium suitable for storing electronicinstructions.

The techniques shown in the figures can be implemented using code anddata stored and executed on one or more electronic devices (e.g., an endstation, a network element). Such electronic devices store andcommunicate (internally and/or with other electronic devices over anetwork) code and data using computer-readable media, such asnon-transitory computer-readable storage media (e.g., magnetic disks;optical disks; random access memory; read only memory; flash memorydevices; phase-change memory) and transitory computer-readabletransmission media (e.g., electrical, optical, acoustical or other formof propagated signals such as carrier waves, infrared signals, digitalsignals). In addition, such electronic devices typically include a setof one or more processors coupled to one or more other components, suchas one or more storage devices (non-transitory machine-readable storagemedia), user input/output devices (e.g., a keyboard, a touchscreen,and/or a display), and network connections. The coupling of the set ofprocessors and other components is typically through one or more bussesand bridges (also termed as bus controllers). Thus, the storage deviceof a given electronic device typically stores code and/or data forexecution on the set of one or more processors of that electronicdevice. Of course, one or more parts of an embodiment may be implementedusing different combinations of software, firmware, and/or hardware.

FIG. 9 illustrates a block diagram of an environment 1010 wherein anon-demand database service might be used. Environment 1010 may includeuser systems 1012, network 1014, system 1016, processor system 1017,application platform 618, network interface 1020, tenant data storage1022, system data storage 1024, program code 1026, and process space1028. In other embodiments, environment 1010 may not have all of thecomponents listed and/or may have other elements instead of, or inaddition to, those listed above.

Environment 1010 is an environment in which an on-demand databaseservice exists. User system 1012 may be any machine or system that isused by a user to access a database user system. For example, any ofuser systems 1012 can be a handheld computing device, a mobile phone, alaptop computer, a workstation, and/or a network of computing devices.As illustrated in herein FIG. 9 (and in more detail in FIG. 10) usersystems 1012 might interact via a network 1014 with an on-demanddatabase service, which is system 1016.

An on-demand database service, such as system 1016, is a database systemthat is made available to outside users that do not need to necessarilybe concerned with building and/or maintaining the database system, butinstead may be available for their use when the users need the databasesystem (e.g., on the demand of the users). Some on-demand databaseservices may store information from one or more tenants stored intotables of a common database image to form a multi-tenant database system(MTS). Accordingly, “on-demand database service 1016” and “system 1016”will be used interchangeably herein. A database image may include one ormore database objects. A relational database management system (RDMS) orthe equivalent may execute storage and retrieval of information againstthe database object(s). Application platform 1018 may be a frameworkthat allows the applications of system 1016 to run, such as the hardwareand/or software, e.g., the operating system. In an embodiment, on-demanddatabase service 1016 may include an application platform 1018 thatenables creation, managing and executing one or more applicationsdeveloped by the provider of the on-demand database service, usersaccessing the on-demand database service via user systems 1012, or thirdparty application developers accessing the on-demand database servicevia user systems 1012.

The users of user systems 1012 may differ in their respectivecapacities, and the capacity of a particular user system 1012 might beentirely determined by permissions (permission levels) for the currentuser. For example, where a salesperson is using a particular user system1012 to interact with system 1016, that user system has the capacitiesallotted to that salesperson. However, while an administrator is usingthat user system to interact with system 1016, that user system has thecapacities allotted to that administrator. In systems with ahierarchical role model, users at one permission level may have accessto applications, data, and database information accessible by a lowerpermission level user, but may not have access to certain applications,database information, and data accessible by a user at a higherpermission level. Thus, different users will have different capabilitieswith regard to accessing and modifying application and databaseinformation, depending on a user's security or permission level.

Network 1014 is any network or combination of networks of devices thatcommunicate with one another. For example, network 1014 can be any oneor any combination of a LAN (local area network), WAN (wide areanetwork), telephone network, wireless network, point-to-point network,star network, token ring network, hub network, or other appropriateconfiguration. As the most common type of computer network in currentuse is a TCP/IP (Transfer Control Protocol and Internet Protocol)network, such as the global internetwork of networks often referred toas the “Internet” with a capital “I,” that network will be used in manyof the examples herein. However, it should be understood that thenetworks that one or more implementations might use are not so limited,although TCP/IP is a frequently implemented protocol.

User systems 1012 might communicate with system 1016 using TCP/IP and,at a higher network level, use other common Internet protocols tocommunicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTPis used, user system 1012 might include an HTTP client commonly referredto as a “browser” for sending and receiving HTTP messages to and from anHTTP server at system 1016. Such an HTTP server might be implemented asthe sole network interface between system 1016 and network 1014, butother techniques might be used as well or instead. In someimplementations, the interface between system 1016 and network 1014includes load-sharing functionality, such as round-robin HTTP requestdistributors to balance loads and distribute incoming HTTP requestsevenly over a plurality of servers. At least as for the users that areaccessing that server, each of the plurality of servers has access tothe MTS' data; however, other alternative configurations may be usedinstead.

In one embodiment, system 1016, shown in FIG. 9, implements a web-basedcustomer relationship management (CRM) system. For example, in oneembodiment, system 616 includes application servers configured toimplement and execute CRM software applications as well as providerelated data, code, forms, webpages and other information to and fromuser systems 1012 and to store to, and retrieve from, a database systemrelated data, objects, and Webpage content. With a multi-tenant system,data for multiple tenants may be stored in the same physical databaseobject, however, tenant data typically is arranged so that data of onetenant is kept logically separate from that of other tenants so that onetenant does not have access to another tenant's data, unless such datais expressly shared. In certain embodiments, system 1016 implementsapplications other than, or in addition to, a CRM application. Forexample, system 1016 may provide tenant access to multiple hosted(standard and custom) applications, including a CRM application. User(or third party developer) applications, which may or may not includeCRM, may be supported by the application platform 618, which managescreation, storage of the applications into one or more database objectsand executing of the applications in a virtual machine in the processspace of the system 1016.

One arrangement for elements of system 1016 is shown in FIG. 9,including a network interface 1020, application platform 1018, tenantdata storage 1022 for tenant data 1023, system data storage 1024 forsystem data 1025 accessible to system 1016 and possibly multipletenants, program code 1026 for implementing various functions of system1016, and a process space 1028 for executing MTS system processes andtenant-specific processes, such as running applications as part of anapplication hosting service. Additional processes that may execute onsystem 1016 include database-indexing processes.

Several elements in the system shown in FIG. 9 include conventional,well-known elements that are explained only briefly here. For example,each user system 1012 could include a desktop personal computer,workstation, laptop, PDA, cell phone, or any wireless access protocol(WAP) enabled device or any other computing device capable ofinterfacing directly or indirectly to the Internet or other networkconnection. User system 1012 typically runs an HTTP client, e.g., abrowsing program, such as Microsoft's Internet Explorer browser,Netscape's Navigator browser, Opera's browser, or a WAP-enabled browserin the case of a cell phone, PDA or other wireless device, or the like,allowing a user (e.g., subscriber of the multi-tenant database system)of user system 1012 to access, process and view information, pages andapplications available to it from system 1016 over network 1014. Usersystem 1012 further includes Mobile OS (e.g., iOS® by Apple®, Android®,WebOS® by Palm®, etc.). Each user system 1012 also typically includesone or more user interface devices, such as a keyboard, a mouse,trackball, touch pad, touch screen, pen or the like, for interactingwith a graphical user interface (GUI) provided by the browser on adisplay (e.g., a monitor screen, LCD display, etc.) in conjunction withpages, forms, applications and other information provided by system 1016or other systems or servers. For example, the user interface device canbe used to access data and applications hosted by system 1016, and toperform searches on stored data, and otherwise allow a user to interactwith various GUI pages that may be presented to a user. As discussedabove, embodiments are suitable for use with the Internet, which refersto a specific global internetwork of networks. However, it should beunderstood that other networks can be used instead of the Internet, suchas an intranet, an extranet, a virtual private network (VPN), anon-TCP/IP based network, any LAN or WAN or the like.

According to one embodiment, each user system 1012 and all of itscomponents are operator configurable using applications, such as abrowser, including computer code run using a central processing unitsuch as an Intel Core® processor or the like. Similarly, system 1016(and additional instances of an MTS, where more than one is present) andall of their components might be operator configurable usingapplication(s) including computer code to run using a central processingunit such as processor system 1017, which may include an Intel Pentium®processor or the like, and/or multiple processor units. A computerprogram product embodiment includes a machine-readable storage medium(media) having instructions stored thereon/in which can be used toprogram a computer to perform any of the processes of the embodimentsdescribed herein. Computer code for operating and configuring system1016 to intercommunicate and to process webpages, applications and otherdata and media content as described herein are preferably downloaded andstored on a hard disk, but the entire program code, or portions thereof,may also be stored in any other volatile or non-volatile memory mediumor device as is well known, such as a ROM or RAM, or provided on anymedia capable of storing program code, such as any type of rotatingmedia including floppy disks, optical discs, digital versatile disk(DVD), compact disk (CD), microdrive, and magneto-optical disks, andmagnetic or optical cards, nanosystems (including molecular memory ICs),or any type of media or device suitable for storing instructions and/ordata. Additionally, the entire program code, or portions thereof, may betransmitted and downloaded from a software source over a transmissionmedium, e.g., over the Internet, or from another server, as is wellknown, or transmitted over any other conventional network connection asis well known (e.g., extranet, VPN, LAN, etc.) using any communicationmedium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as arewell known. It will also be appreciated that computer code forimplementing embodiments can be implemented in any programming languagethat can be executed on a client system and/or server or server systemsuch as, for example, C, C++, HTML, any other markup language, Java™,JavaScript, ActiveX, any other scripting language, such as VBScript, andmany other programming languages as are well known may be used. (Java™is a trademark of Sun Microsystems, Inc.).

According to one embodiment, each system 1016 is configured to providewebpages, forms, applications, data and media content to user (client)systems 1012 to support the access by user systems 1012 as tenants ofsystem 1016. As such, system 1016 provides security mechanisms to keepeach tenant's data separate unless the data is shared. If more than oneMTS is used, they may be located in close proximity to one another(e.g., in a server farm located in a single building or campus), or theymay be distributed at locations remote from one another (e.g., one ormore servers located in city A and one or more servers located in cityB). As used herein, each MTS could include one or more logically and/orphysically connected servers distributed locally or across one or moregeographic locations. Additionally, the term “server” is meant toinclude a computer system, including processing hardware and processspace(s), and an associated storage system and database application(e.g., OODBMS or RDBMS) as is well known in the art. It should also beunderstood that “server system” and “server” are often usedinterchangeably herein. Similarly, the database object described hereincan be implemented as single databases, a distributed database, acollection of distributed databases, a database with redundant online oroffline backups or other redundancies, etc., and might include adistributed database or storage network and associated processingintelligence.

FIG. 10 also illustrates environment 1010. However, in FIG. 10 elementsof system 1016 and various interconnections in an embodiment are furtherillustrated. FIG. 10 shows that user system 1012 may include processorsystem 1012A, memory system 1012B, input system 1012C, and output system1012D. FIG. 10 shows network 1014 and system 1016. FIG. 10 also showsthat system 1016 may include tenant data storage 1022, tenant data 1023,system data storage 1024, system data 1025, User Interface (UI) 1130,Application Program Interface (API) 1132, PL/SOQL 1134, save routines1136, application setup mechanism 1138, applications servers 1100 ₁-1100_(N), system process space 1102, tenant process spaces 1104, tenantmanagement process space 1110, tenant storage area 1112, user storage1114, and application metadata 1116. In other embodiments, environment1010 may not have the same elements as those listed above and/or mayhave other elements instead of, or in addition to, those listed above.

User system 1012, network 1014, system 1016, tenant data storage 1022,and system data storage 1024 were discussed above in FIG. 9. Regardinguser system 1012, processor system 1012A may be any combination of oneor more processors. Memory system 1012B may be any combination of one ormore memory devices, short term, and/or long term memory. Input system1012C may be any combination of input devices, such as one or morekeyboards, mice, trackballs, scanners, cameras, and/or interfaces tonetworks. Output system 1012D may be any combination of output devices,such as one or more monitors, printers, and/or interfaces to networks.As shown by FIG. 9, system 1016 may include a network interface 1020 (ofFIG. 9) implemented as a set of HTTP application servers 1100, anapplication platform 1018, tenant data storage 1022, and system datastorage 1024. Also shown is system process space 1102, includingindividual tenant process spaces 1104 and a tenant management processspace 1110. Each application server 1100 may be configured to tenantdata storage 1022 and the tenant data 1023 therein, and system datastorage 1024 and the system data 1025 therein to serve requests of usersystems 1012. The tenant data 1023 might be divided into individualtenant storage areas 1112, which can be either a physical arrangementand/or a logical arrangement of data. Within each tenant storage area1112, user storage 1114 and application metadata 1116 might be similarlyallocated for each user. For example, a copy of a user's most recentlyused (MRU) items might be stored to user storage 1114. Similarly, a copyof MRU items for an entire organization that is a tenant might be storedto tenant storage area 1112. A UI 1130 provides a user interface and anAPI 71132 provides an application programmer interface to system 1016resident processes to users and/or developers at user systems 1012. Thetenant data and the system data may be stored in various databases, suchas one or more Oracle™ databases.

Application platform 1018 includes an application setup mechanism 1138that supports application developers' creation and management ofapplications, which may be saved as metadata into tenant data storage1022 by save routines 1136 for execution by subscribers as one or moretenant process spaces 1104 managed by tenant management process 1110 forexample. Invocations to such applications may be coded using PL/SOQL1134 that provides a programming language style interface extension toAPI 1132. A detailed description of some PL/SOQL language embodiments isdiscussed in commonly owned U.S. Pat. No. 7,730,478 entitled, “Methodand System for Allowing Access to Developed Applicants via aMulti-Tenant Database On-Demand Database Service”, issued Jun. 1, 2010to Craig Weissman, which is incorporated in its entirety herein for allpurposes. Invocations to applications may be detected by one or moresystem processes, which manage retrieving application metadata 1116 forthe subscriber making the invocation and executing the metadata as anapplication in a virtual machine.

Each application server 1100 may be communicably coupled to databasesystems, e.g., having access to system data 1025 and tenant data 1023,via a different network connection. For example, one application server1100 ₁ might be coupled via the network 1014 (e.g., the Internet),another application server 1100 _(N-1) might be coupled via a directnetwork link, and another application server 1100 _(N) might be coupledby yet a different network connection. Transfer Control Protocol andInternet Protocol (TCP/IP) are typical protocols for communicatingbetween application servers 1100 and the database system. However, itwill be apparent to one skilled in the art that other transportprotocols may be used to optimize the system depending on the networkinterconnect used.

In certain embodiments, each application server 1100 is configured tohandle requests for any user associated with any organization that is atenant. Because it is desirable to be able to add and remove applicationservers from the server pool at any time for any reason, there ispreferably no server affinity for a user and/or organization to aspecific application server 1100. In one embodiment, therefore, aninterface system implementing a load balancing function (e.g., an F5Big-IP load balancer) is communicably coupled between the applicationservers 1100 and the user systems 1012 to distribute requests to theapplication servers 1100. In one embodiment, the load balancer uses aleast connections algorithm to route user requests to the applicationservers 1100. Other examples of load balancing algorithms, such as roundrobin and observed response time, also can be used. For example, incertain embodiments, three consecutive requests from the same user couldhit three different application servers 1100, and three requests fromdifferent users could hit the same application server 1100. In thismanner, system 1016 is multi-tenant, wherein system 1016 handles storageof, and access to, different objects, data and applications acrossdisparate users and organizations.

As an example of storage, one tenant might be a company that employs asales force where each salesperson uses system 1016 to manage theirsales process. Thus, a user might maintain contact data, leads data,customer follow-up data, performance data, goals and progress data,etc., all applicable to that user's personal sales process (e.g., intenant data storage 1022). In an example of a MTS arrangement, since allof the data and the applications to access, view, modify, report,transmit, calculate, etc., can be maintained and accessed by a usersystem having nothing more than network access, the user can manage hisor her sales efforts and cycles from any of many different user systems.For example, if a salesperson is visiting a customer and the customerhas Internet access in their lobby, the salesperson can obtain criticalupdates as to that customer while waiting for the customer to arrive inthe lobby.

While each user's data might be separate from other users' dataregardless of the employers of each user, some data might beorganization-wide data shared or accessible by a plurality of users orall of the users for a given organization that is a tenant. Thus, theremight be some data structures managed by system 1016 that are allocatedat the tenant level while other data structures might be managed at theuser level. Because an MTS might support multiple tenants includingpossible competitors, the MTS should have security protocols that keepdata, applications, and application use separate. Also, because manytenants may opt for access to an MTS rather than maintain their ownsystem, redundancy, up-time, and backup are additional functions thatmay be implemented in the MTS. In addition to user-specific data andtenant specific data, system 1016 might also maintain system level datausable by multiple tenants or other data. Such system level data mightinclude industry reports, news, postings, and the like that are sharableamong tenants.

In certain embodiments, user systems 1012 (which may be client systems)communicate with application servers 1100 to request and updatesystem-level and tenant-level data from system 1016 that may requiresending one or more queries to tenant data storage 1022 and/or systemdata storage 1024. System 1016 (e.g., an application server 1100 insystem 1016) automatically generates one or more SQL statements (e.g.,one or more SQL queries) that are designed to access the desiredinformation. System data storage 1024 may generate query plans to accessthe requested data from the database.

Each database can generally be viewed as a collection of objects, suchas a set of logical tables, containing data fitted into predefinedcategories. A “table” is one representation of a data object, and may beused herein to simplify the conceptual description of objects and customobjects. It should be understood that “table” and “object” may be usedinterchangeably herein. Each table generally contains one or more datacategories logically arranged as columns or fields in a viewable schema.Each row or record of a table contains an instance of data for eachcategory defined by the fields. For example, a CRM database may includea table that describes a customer with fields for basic contactinformation such as name, address, phone number, fax number, etc.Another table might describe a purchase order, including fields forinformation such as customer, product, sale price, date, etc. In somemulti-tenant database systems, standard entity tables might be providedfor use by all tenants. For CRM database applications, such standardentities might include tables for Account, Contact, Lead, andOpportunity data, each containing pre-defined fields. It should beunderstood that the word “entity” may also be used interchangeablyherein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to createand store custom objects, or they may be allowed to customize standardentities or objects, for example by creating custom fields for standardobjects, including custom index fields. U.S. patent application Ser. No.10/817,161, filed Apr. 2, 2004, entitled “Custom Entities and Fields ina Multi-Tenant Database System”, and which is hereby incorporated hereinby reference, teaches systems and methods for creating custom objects aswell as customizing standard objects in a multi-tenant database system.In certain embodiments, for example, all custom entity data rows arestored in a single multi-tenant physical table, which may containmultiple logical tables per organization. It is transparent to customersthat their multiple “tables” are in fact stored in one large table orthat their data may be stored in the same table as the data of othercustomers.

Any of the above embodiments may be used alone or together with oneanother in any combination. Embodiments encompassed within thisspecification may also include embodiments that are only partiallymentioned or alluded to or are not mentioned or alluded to at all inthis brief summary or in the abstract. Although various embodiments mayhave been motivated by various deficiencies with the prior art, whichmay be discussed or alluded to in one or more places in thespecification, the embodiments do not necessarily address any of thesedeficiencies. In other words, different embodiments may addressdifferent deficiencies that may be discussed in the specification. Someembodiments may only partially address some deficiencies or just onedeficiency that may be discussed in the specification, and someembodiments may not address any of these deficiencies.

While one or more implementations have been described by way of exampleand in terms of the specific embodiments, it is to be understood thatone or more implementations are not limited to the disclosedembodiments. To the contrary, it is intended to cover variousmodifications and similar arrangements as would be apparent to thoseskilled in the art. Therefore, the scope of the appended claims shouldbe accorded the broadest interpretation so as to encompass all suchmodifications and similar arrangements. It is to be understood that theabove description is intended to be illustrative, and not restrictive.

What is claimed is:
 1. A non-transitory computer-readable medium havingstored thereon instructions that, when executed by one or moreprocessors, are configurable to cause the one or more processors to:transmit one or more log event messages to a computing device, whereineach of the one or more log event messages comprises a unique identifier(ID); generate a comparison checksum for each of the one or more logevent messages, wherein each comparison checksum is associated with aunique ID corresponding to a log event message from which the comparisonchecksum was generated; perform an encryption on each comparisonchecksum and associated unique ID pair to generate encryption dataincluding the encrypted checksum and associated unique ID; and transmitthe encryption data to the computing device, wherein the encrypted datais transmitted to the computing device as a separate batch processingworkflow via a separate channel from the transmitted one or more logevent messages.
 2. The non-transitory computer-readable medium of claim1, having stored thereon instructions that, when executed by one or moreprocessors, are configurable to further cause the one or more processorsto store the comparison checksums and the associated unique IDs as abatch.
 3. The non-transitory computer-readable medium of claim 2,wherein performing the encryption comprises applying a Salt algorithm oneach checksum and associated unique ID to generate the encryption data.4. The non-transitory computer-readable medium of claim 3, whereinperforming the encryption further comprises performing a symmetric keyencryption on the batch via a public key associated with the computingdevice.
 5. A non-transitory computer-readable medium having storedthereon instructions that, when executed by one or more processors, areconfigurable to cause the one or more processors to: receive one or morelog event messages at a computing device, wherein each of the one ormore log event messages comprises a unique identifier (ID); generate afirst message checksum for a first of the one or more log eventmessages, wherein the first log event message and the first messagechecksum are associated with a first unique ID; receive encryption datafrom the computing device, wherein the encrypted data is received via aseparate channel from the received one or more log event messages;perform a decryption of the encryption data to extract one or morecomparison checksum and associated unique ID pairs; and compare a firstof the one or more comparison checksums having the first unique ID tothe first message checksum to determine whether there is a match betweenthe first message checksum and the first comparison checksum.
 6. Thenon-transitory computer-readable medium of claim 5, having storedthereon instructions that, when executed by one or more processors, areconfigurable to further cause the one or more processors to: generate asecond message checksum for a second of the one or more messages,wherein the second message and the second message checksum areassociated with a second unique ID; and compare a second of the one ormore comparison checksums having the second unique ID to the secondmessage checksum to determine whether there is a match between thesecond message checksum and the second comparison checksum.
 7. Thenon-transitory computer-readable medium of claim 6, having storedthereon instructions that, when executed by one or more processors, areconfigurable to further cause the one or more processors to generate areport a result of the comparison between the first message checksum andthe first comparison checksum and the second message checksum and thesecond comparison checksum.
 8. The non-transitory computer-readablemedium of claim 5, having stored thereon instructions that, whenexecuted by one or more processors, are configurable to further causethe one or more processors to store the first message, the first messagechecksum and the first unique ID prior to receiving the encryption data.9. A computing device comprising: at least one physical memory device tostore a log emitter; and one or more processors coupled with the atleast one physical memory device, the one or more processorsconfigurable to execute the log emitter to transmit one or more logevent messages to a computing device, generate a comparison checksum foreach of the one or more log event messages, perform an encryption oneach comparison checksum and an associated unique identifier (ID) pairto generate encryption data including the encrypted checksum andassociated unique ID and transmit the encryption data to the computingdevice, wherein the encrypted data is transmitted to the computingdevice as a separate batch processing workflow via a separate channelfrom the transmitted one or more log event messages, and wherein each ofthe one or more log event messages comprises a unique ID and eachcomparison checksum is associated with a unique ID corresponding to alog event message from which the comparison checksum was generated. 10.The computing device of claim 9, wherein the log emitter stores thecomparison checksums and the associated unique IDs as a batch.
 11. Thecomputing device of claim 10, wherein performing the encryptioncomprises applying a Salt algorithm on each checksum and associatedunique ID to generate the encryption data.
 12. The computing device ofclaim 11, wherein performing the encryption further comprises performinga symmetric key encryption on the batch via a public key associated withthe computing device.
 13. A computing device comprising: at least onephysical memory device to store a log collector; and one or moreprocessors coupled with the at least one physical memory device, the oneor more processors configurable to execute the log collector to receiveone or more log event messages at a computing device, generate a firstmessage checksum for a first of the one or more log event messages,receive encryption data from the computing device, wherein the encrypteddata is received via a separate channel from the received one or morelog event messages, perform a decryption of the encryption data toextract one or more comparison checksum and associated unique ID pairsand compare a first of the one or more comparison checksums having afirst unique identifier (ID) to the first message checksum to determinewhether there is a match between the first message checksum and thefirst comparison checksum, wherein each of the one or more messagescomprises a unique ID and the first message and the first messagechecksum are associated with the first unique ID.
 14. The computingdevice of claim 13, wherein the log collector further generates a secondmessage checksum for a second of the one or more messages, wherein thesecond message and the second message checksum are associated with asecond unique ID and compares a second of the one or more comparisonchecksums having the second unique ID to the second message checksum todetermine whether there is a match between the second message checksumand the second comparison checksum.
 15. The computing device of claim14, wherein the log collector generates a report a result of thecomparison between the first message checksum and the first comparisonchecksum and the second message checksum and the second comparisonchecksum.
 16. The computing device of claim 13, wherein the logcollector stores the first message, the first message checksum and thefirst unique ID prior to receiving the encryption data.